Subject identification systems and methods

ABSTRACT

Disclosed techniques relate to identifying subjects in digital images. In various embodiments, a first camera ( 276, 376, 476, 976 ) may acquire ( 1002 ) digital images ( 420 ) depicting a subject in an area. Portion(s) of the digital image(s) that depict a face of the subject may be detected ( 1004 ) as detected face image(s). Features of the detected face image(s) may be compared ( 1006 ) with features of subject reference templates associated with subject(s) in a subject reference database ( 412 ). The subject reference database stores subject reference templates that are associated with multiple subjects and that are generated based on data received from a second camera ( 256, 456 ). Based on the comparing, an identity of the subject may be determined ( 1014 ) and the features of the detected face image(s) may be stored ( 1016 ) in the subject reference database in association with the subject, e.g., as an auxiliary template feature vector for later use.

CROSS-REFERENCE TO PRIOR APPLICATIONS

This application is the U.S. National Phase application under 35 U.S.C. § 371 of International Application No. PCT/EP2018/074148, filed on Sep. 7, 2018, which claims the benefit of U.S. Provisional Patent Application No. 62/557,958, filed on Sep. 13, 2017. These applications are hereby incorporated by reference herein.

FIELD

The present disclosure is directed generally, but not exclusively, to identifying people in digital images (including streams of digital images). More particularly, but not exclusively, various methods and apparatus disclosed herein relate to identifying people in digital images (or streams thereof) so that those people can be located in areas such as waiting rooms of a hospital.

BACKGROUND

There are a number of scenarios in which it may be desirable to automatically identify people (or “subjects”) based on digital images that capture scenes containing people. For example, when patients visit a hospital, they typically are registered, triaged, and then sent to an area such as a waiting room to wait for hospital resources such as physicians to become available to examine and/or treat the patients. Being able to automatically identify individual patients may be helpful for continuing to monitor their conditions (e.g., for deterioration) while they wait for allocation of medical resources. It may also be helpful for determining if/when patients left without being seen (LWBS). Automatically identifying people based on digital images may also be useful in a variety of other contexts, such as airports, train stations, border crossings, gyms and fitness centers, various businesses, etc.

In some contexts, it may be desired to identify individual subjects in digital images that contain multiple subjects. For example, digital images captured by a camera in a waiting room are likely to depict, in addition to waiting patients, other people such as friends, relatives, etc. that might be waiting with the patients. Face detection techniques may detect all the faces in the digital images, but it may not be clear which faces belong to patients and which belong to others. Moreover, subjects in monitored areas such as waiting rooms are not likely going to be looking at the camera. Instead they may be looking at their phones, magazines, each other, etc. Thus, even when depicted faces are detected, the detected faces as depicted in their raw state may appear substantially different than in intake images acquired at registration, e.g., when the subject may be looking directly at a camera. In addition, the light conditions in the area may vary across time (e.g., daytime versus nighttime) and/or across the physical space.

SUMMARY

The present disclosure is directed to methods, systems, and apparatus for automatically identifying people depicted in acquired digital images. As one non-limiting example, a plurality of triaged patients may wait in a waiting room until they can be seen by an emergency medicine physician. The patients may be included in a patient monitoring queue (also referred to simply as a “patient queue”) that is ordered or ranked, for instance, based on a measure of acuity associated with each patient (referred to herein as a “patient acuity measure”) that is determined based on information obtained/acquired from the patient by a triage nurse, as well as other data points such as patient waiting time, patient presence, etc. One or more “vital sign acquisition cameras” mounted in the waiting room may be configured to periodically perform contactless and/or unobtrusive acquisition of one more updated vital signs and/or physiological parameters from each patient. These updated vital signs and/or physiological parameters may include but are not limited to temperature, pulse rate, oxygen saturation (“SpO₂”), respiration rate, posture, perspiration and so forth.

In order to identify a particular patient from which the vital sign acquisition camera(s) should acquire updated vital signs, techniques described herein may be employed to match “registered” subjects—e.g., registered and/or triaged patients—to “detected” subjects depicted in a scene captured in one or more digital images acquired by one or more cameras. More generally, techniques described herein may be implemented in various contexts to identify subjects depicted in digital images (e.g., single images and/or streams of digital images, such as video feeds), e.g., by collecting subject reference templates and corresponding template feature vectors associated with each subject to be monitored (which may be referred to herein as “registered subjects”) and later using those subject reference templates and/or corresponding template feature vectors to identify the subject in subsequently captured digital images.

Generally, in one aspect, a method may include: acquiring, using a first camera, one or more digital images that depict a subject in an area; detecting, as one or more detected face images associated with the subject, one or more portions of the one or more digital images that depict a face of the subject; comparing features of the one or more detected face images with features of subject reference templates associated with one or more subjects in a subject reference database, wherein the subject reference database stores subject reference templates related to a plurality of subjects, and wherein the subject reference templates stored in the subject reference database are generated based on data received from a second camera; and based on the comparing: determining an identity of the subject, and storing the features of the one or more detected face images in the subject reference database in association with the subject as an auxiliary template feature vector for later use.

In various embodiments, the comparing may include: applying the one or more detected face images as input across a neural network to generate one or more corresponding face feature vectors; and applying at least some of the subject reference templates as input across the neural network to generate a plurality of corresponding template feature vectors. In various embodiments, the neural network may take the form of a convolutional neural network.

In various embodiments, the second camera may be located in a registration or triage area . . . . In various embodiments, the first camera may located in a waiting room or general ward. In various embodiments, the method may further include: acquiring, using the first camera, one or more subsequent digital images that depict a second subject in the area; detecting, as one or more detected face images associated with the second subject, one or more portions of the one or more subsequent digital images that depict a face of the second subject; and comparing features of the one or more detected face images associated with the second subject with features of auxiliary subject reference templates associated with one or more subjects in the subject reference database, wherein the auxiliary subject reference templates are generated based on digital images captured by the first camera to determine an identity of the second subject.

In various embodiments, the auxiliary template feature vector may replace an existing template feature vector associated with the subject. In various embodiments, the comparing may include: determining a first distance between a face feature vector generated from one or more of the detected face images and a first template feature vector generated from a first subject reference template associated with a first subject in the subject reference database; and determining a second distance between the face feature vector and a second template feature vector generated from a subject reference template associated with a second subject in the subject reference database. In various embodiments, the storing may be based on a relationship between the first and second distances.

It should be appreciated that all combinations of the foregoing concepts and additional concepts discussed in greater detail below (provided such concepts are not mutually inconsistent) are contemplated as being part of the subject matter disclosed herein. In particular, all combinations of claimed subject matter appearing at the end of this disclosure are contemplated as being part of the subject matter disclosed herein. It should also be appreciated that terminology explicitly employed herein that also may appear in any disclosure incorporated by reference should be accorded a meaning most consistent with the particular concepts disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, like reference characters generally refer to the same parts throughout the different views. Also, the drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the disclosure.

FIG. 1 schematically illustrates a general process flow for monitoring patients identified in digital images using disclosed techniques, in accordance with various embodiments.

FIG. 2 illustrates an example environment in which various components of the present disclosure may implement selected aspects of the present disclosure, in accordance with various implementations.

FIG. 3 depicts an example scenario in which disclosed techniques may be practiced, in accordance with various embodiments.

FIG. 4 depicts example components and operations for performing various aspects of the present disclosure.

FIG. 5 depicts an example of how subject reference templates and corresponding template feature vectors may be generated from intake digital images, in accordance with various embodiments.

FIG. 6 depicts an example of how a subject may be detected entering and/or leaving a camera's field of view, in accordance with various embodiments.

FIG. 7 depicts one example of how a detected face image may be normalized, e.g., to be front-facing, in accordance with various embodiments.

FIG. 8 depicts, in greater detail than FIG. 5, an example of how subject reference templates may be selected from intake digital images, in accordance with various embodiments.

FIG. 9 depicts one example of how subjects may be identified in an area being monitored, in accordance with various embodiments.

FIG. 10 depicts an example method for performing selected aspects of the present disclosure, in accordance with various embodiments.

FIG. 11 depicts components of an example computer system.

DETAILED DESCRIPTION

FIG. 1 schematically illustrates generally how patients may be monitored using disclosed techniques. In particular, operations and actions are depicted that may occur in a pre-waiting room area, such as at a pre-waiting room area(s) 102, which may include reception and/or registration, and/or a triage station or booth. In addition, operations and actions are depicted that may occur in a waiting room 104. It should be understood that the sequence of FIG. 1 is not meant to be limiting, and other sequences are possible.

At block 106, a new patient may enter and/or approach pre-waiting room area(s) 102, e.g., after checking in at a reception desk (not depicted). At block 108, the new patient may be registered. Registration may include, for instance, collecting information about the patient such as the patient's name, age, gender, insurance information, and reason for visit. Typically, but not exclusively, this information may be manually input into a computer by medical personnel such as receptionist or registrar. In some embodiments, one or more reference digital images of the patient may be acquired, e.g., by a camera that is integral with a computing device operated by the triage nurse, by a standalone camera, and/or by a vital sign acquisition camera (in which case at least some vital signs may be optionally acquired at registration). As will be described in more detail below, in some embodiments, the digital images acquired by the camera during registration at block 108 may be referred to as “intake digital images.” Subsets of these intake digital images—and in some cases, selected sub-portions of these images that depict, for instance, faces—may be selectively retained as “subject reference templates” that can be used later to identify patients (or more generally, “subjects”) in areas such as waiting room 104.

In many instances, the triage nurse additionally may acquire various initial vital signs and/or physiological parameters at block 110 using various medical instruments. These initial vital signs and/or physiological parameters may include but are not limited to blood pressure, pulse, glucose level, SpO₂, photoplethysmogram (“PPG”), respiration rate (e.g., breathing rate), temperature, skin color, and so forth. While not depicted in FIG. 1, in some embodiments, other information may be gathered at triage as well, such as acquiring/updating a patient's medical history, determining patient allergies, determining patient's use of medications, and so forth. In some embodiments, the patient may be assigned a so-called “patient acuity measure,” which may be a measure that is used to rank a severity of the patient's ailment, and in some instances may indicate an anticipated need for emergency room resources. Any number of commonly used indicators and/or clinician decision support (“CDS”) algorithms may be used to determine and/or assign a patient acuity measure, including but not limited to the Emergency Severity Index (“ESI”), the Taiwan Triage System (“TTS”), the Canadian Triage and Acuity Scale (“CTAS”), and so forth. For example, in some embodiments, vital signs of the patient may be compared with predefined vital sign thresholds stored in a system database, or with published or known vital sign values typical for a given patient age, gender, weight, etc., to determine the patient's initial patient acuity measure and/or the patient's initial position in the patient queue. In some embodiments, various physiological and other information about the patient may be applied as input across a trained model (e.g., regression model, neural network, deep learning network, etc.), case-based reasoning algorithm, or other clinical reasoning algorithm to derive one or more acuity measures. In some embodiments, the information used for deriving the acuity measure may include or even be wholly limited to vitals or other information that may be captured by the vital sign acquisition camera. In some embodiments, the information used for deriving the acuity measure may alternatively or additionally include information such as information from a previous electronic medical record (“EMR”) of the patient, information acquired from the patient at triage, information from wearable devices or other sensors carried by the patient, information about other patients or people in the waiting room (e.g., vitals of others in the room), information about family members or others associated with the patient (e.g., family member EMRs), etc.

Once the patient is registered and/or triaged, at block 112, the patient may be sent to waiting room 104. In many scenarios, the operations of FIG. 1 may occur in slightly different orders. For example, in some instances, a patient may first be registered, then go to a waiting room until they can be triaged, and then be sent to a doctor some time after triage (either immediately or after being sent back to the waiting room). In some situations, such as emergency situations (e.g., during disasters), patients may go straight to triage and then to a doctor, and may only be registered later when the patient has been stabilized.

At block 114, it may be determined, e.g., using one or more cameras, sensors, or input from medical personnel, that a patient has left the waiting room. Block 114 may include scanning each person currently within the waiting room (e.g., as part of a seeking function that attempts to locate the patient once the patient is at the top of a queue of patients for which vitals are to be captured, such as an execution of block 120 described below, or cycling through each person in the room to capture vitals, as multiple executions of the loop including blocks 118 and 120 described below) and determining that the patient was not located. In some embodiments, the system may wait until a predetermined number of instances of the patient missing is reached or a predetermined amount of time has passed during which the patient is missing before the patient is deemed to have left the waiting room to account for temporary absences (e.g., visiting the restroom or speaking with clinical staff). For example, the patient may have been taken into the ER proper because it is their turn to see a doctor. Or the patient's condition may have improved while they waited, causing them to leave the hospital. Or the patient may have become impatient and left to seek care elsewhere. Whatever the reason, once it is determined that the patient has left the waiting room for at least a threshold amount of time, at block 116, the patient may be deemed to have left without being seen and may be released from the system, e.g., by removing them from a queue in which registered patients are entered.

At block 118, one or more patients in waiting room 104 may be selected for monitoring. For example, in some embodiments, a database (e.g., subject reference database 412 in FIG. 4) storing registration information obtained at blocks 108-110 may be searched to select a patient having the highest patient acuity measure or a patient having the highest acuity measured that has not been monitored recently, as may be determined by a time threshold set for all patients or set (e.g., inversely correlated) based on the acuity measure. In other embodiments, registration information associated with a plurality of patients in the waiting room may be ranked in a patient monitoring queue, e.g., by their respective patient acuity measures, in addition to or instead of other measures such as waiting times, patient presence in the waiting room (e.g., missing patients may be selected for monitoring more frequently to determine whether they should be released if repeatedly absent), etc. In yet other embodiments, patient acuity measures may not be considered when ranking the patient monitoring queue, and instead only considerations of patient waiting times, patient presence, etc., may be considered. In still other embodiments, patients may simply be selected one-by-one, e.g., in a predetermined scanning order that is dictated, for instance, by a sequence of chairs or couches in waiting room 104.

However such a patient monitoring queue is ranked, in some embodiments, the first patient in the queue may be selected as the one to be monitored next. It is not required (though it is possible) that the patient monitoring queue be stored in sequence of physical memory locations ordered by patient acuity measures. Rather, in some embodiments, a ranked patient monitoring queue may merely include a rank or priority level value associated with each patient. In other words, a “patient monitoring queue” as described herein may refer to a “logical” queue that is logically ranked based on patient acuity measures, waiting time etc., not necessarily a contiguous sequence of memory locations. Patients may be selected for monitoring at block 118 in an order of their respective ranking in the patient monitoring queue.

At block 120, the patient selected at block 118 may be located in waiting room 104. In various embodiments, one or more cameras, such as one or more vital sign acquisition cameras (not depicted in FIG. 1, see FIGS. 2, and 3) or other more conventional cameras that are deployed in or near waiting room 104, may be operated (e.g., panned, tilted, zoomed, etc.) to acquire one or more digital images of patients in waiting room 104. As will be described in more detail below, those acquired digital images may be compared to one or more reference patient images (often referred to herein as “subject reference templates”) captured during registration at block 108. In some embodiments, features of those acquired digital images that are extracted using a machine learning model, such as a trained convolutional neural network, may be compared to similarly-extracted features of subject reference templates associated with registered patients.

At block 122, one or more vital sign acquisition cameras mounted or otherwise deployed in or near waiting room 104 may be operated to perform unobtrusive (e.g., contactless) acquisition of one or more updated vital signs and/or physiological parameters from the patient selected at block 118 and located at block 120. These vital sign acquisition cameras may be configured to acquire (without physically contacting the patient) a variety of different vital signs and/or physiological parameters from the patient, including but not limited to blood pressure, pulse (or heart) rate, skin color, respiratory rate, SpO₂, temperature, posture, sweat levels, and so forth. In some embodiments, vital sign acquisition cameras may be equipped to perform so-called “contactless methods” to acquire vital signs and/or extract physiological information from a patient may be used as medical image devices. Non-limiting examples of such cameras are described in United States Patent Application Publication Nos. 20140192177A1, 20140139656A1, 20140148663A1, 20140253709A1, 20140235976A1, and U.S. Pat. No. 9,125,606B2, which are incorporated herein by reference for all purposes.

At block 124, it may be determined, e.g., by one or more components depicted in FIG. 2 (described below), based on a comparison of the updated vital sign(s) and/or physiological parameters acquired at block 122 to previously-acquired vital signs and/or physiological parameters (e.g., the initial vital signs acquired at block 110 or a previous iteration of updated vital signs/physiological parameters acquired by the vital sign acquisition cameras), whether the patient's condition has changed. For example, it may be determined whether the patient's pulse rate, respiratory rate, blood pressure, SpO₂, PPG, temperature, etc. has increased or decreased while the patient has waited. If the answer is no, then control may proceed back to block 118, and a new patient (e.g., the patient with the next highest patient acuity measure) may be selected and control may proceed back to block 120. However, if the answer at block 124 is yes (i.e. the patient's condition has changed), then control may pass to block 126. In some embodiments, the patient's condition may be represented (at least partially) by the same acuity measure used for purposes of determining monitoring order.

At block 126, it may be determined (again, by one or more components of FIG. 2) whether a medical alert is warranted based on the change detected at block 124. For example, it may be determined whether a change in one or more vital signs or patient acuity measures satisfies one or more thresholds (e.g., has blood pressure increased above a level that is considered safe for this particular patient?). If the answer is yes, then control may pass to block 128. At block 128, an alarm may be output, e.g., to a duty nurse or other medical personnel, that the patient is deteriorating. The medical personnel may then check on the patient to determine if remedial action, such as immediately admitting to the ED to see a doctor, is warranted. In some embodiments, control may then pass back to block 118. However, if the answer at block 126 is no, then in some embodiments, control may pass back to block 118.

FIG. 2 depicts example components that may be used to practice disclosed techniques, in accordance with various embodiments. A hospital information system 240 may be of the type that is commonly found in hospitals, doctor's offices, and so forth. Hospital information system 240 may be implemented using one or more computing systems that may or may not be connected via one or more computer networks (not depicted). Hospital information system 240 may include, among other things, a registration module 242, a triage module 244, a release module 246, and an alarm module 248. One or more of modules 242-248, or any other module or engine described herein, may be implemented using any combination of hardware and software, including one or more microprocessors executing instructions stored in memory. For example, the registration module 242 may include registration instructions implementing the functionality described herein in connection with registration executing on a processor while the triage module 244 may include triage instructions implementing the functionality described herein in connection with triage executing on the same processor. Similar underlying hardware and software may be used to implement other “modules” described herein.

Registration module 242 may be configured to receive, e.g., as manual input from a duty nurse, registration information of new patients. This may include, for instance, the patient's name, age, insurance information, and so forth. Triage module 244 may be configured to receive, e.g., as manual input from a duty nurse or directly from networked medical equipment, vital signs such as those described above and/or other physiological data, such as weight, height, the patient's reason for the visit, etc. In various embodiments, vital signs received by triage module 244 and/or a patient acuity measure (e.g., ESI in FIG. 2) may be associated with corresponding patient information received by registration module 242, e.g., in one or more databases (not depicted) associated with hospital information system 240.

Alarm module 248 may be configured to receive information indicative of various events, such as patient deterioration, and raise various alarms and/or alerts in response. These alarms and/or alerts may be output using a variety of modalities, including but not limited to visual output (e.g., on display screens visible to hospital personnel), intercom announcements, text messages, emails, audio alerts, haptic alerts, pages, pop-up windows, flashing lights, and so forth. Modules 242-248 of hospital information system 240 may be operably coupled, e.g., via one or computer networks (not depicted), to a hospital information system interface 250 (“H.I.S. Interface” in FIG. 2).

Hospital information system interface 250 may serve as an interface between the traditional hospital information system 240 and a patient monitoring system 252 configured with selected aspects of the present disclosure. In various embodiments, the hospital information system interface 250 may publish, e.g., to other modules of the patient monitoring system 252, various information about patients such as registration information, patient acuity measures (e.g., ESI), prescribed and/or administered medications, whether a patient has been released, various alarms/alerts, and so forth. As will be described below, in some embodiments, these publications may be provided to an event publish and subscribe (“EPS”) module 270, which may then selectively store them in database 272 and/or selectively publish them to other modules of patient monitoring system 252. In some embodiments, hospital information system interface 250 may additionally or alternatively subscribe to one or more alerts or publications provided by other modules. For example, hospital information system interface 250 may subscribe to alerts from deterioration detection module 268, e.g., so that hospital information system interface 250 may notify appropriate components of hospital information system 240, such as alarm module 248, that a patient is deteriorating. EPS is just one of many possible protocols that could be used for communication among system components, and is not meant to be limiting.

Patient monitoring system 252 may include a variety of components that facilitate monitoring of patients in an area such as waiting room 104 to ensure that patients are served in a manner conducive with their actual medical condition. Patent monitoring system 252 may include, for instance, a patient capture module 254 that interfaces with one or more cameras 256, a patient queue module 258, a patient identification module 260, a dynamic calibration module 262, a face/torso acquisition module 264, a vital signs measurement module 266, a deterioration detection module 268, the aforementioned EPS module 270, and one or more databases 272, 274. As noted above, each of modules 250, 254, and 258-270 may be implemented using any combination of hardware and software. And while these modules are depicted separately, that is not meant to be limiting or to suggest each is implemented on a separate piece of hardware. For example, one or more modules may be combined and/or omitted, and one or more modules may be implemented on one or more computing systems operably connected via one or more computer networks (not depicted). The lines depicted connecting various components of FIG. 2 may represent communication channels accessible to these components. These communication channels may be implemented using any number of networking or other computer communication technologies, such as one or more buses, Ethernet, Wi-Fi, Bluetooth, Z-Wave, ZigBee, cellular communication, and so forth.

Patient monitoring system 252 may also include one or more vital sign acquisition cameras 276 that are configured to acquire, from some distance from a patient, one or more vital signs and/or physiological parameters of the patient. Examples of such vital sign acquisition cameras were described above. In various embodiments, a vital sign acquisition camera 276 may be a pan-tilt-zoom (“PTZ”) camera that is operable to pan, tilt, and zoom so that different parts of an area such as waiting room 104 are contained within its FOV. In this manner, it is possible to scan the area being monitored to locate different patients, so that updated vital signs and/or physiological parameters may be acquired unobtrusively.

Patient capture module 254 may receive, from one or more cameras 256, one or more signals carrying captured image data of a patient. For example, in some embodiments, patient capture module 254 may receive a video stream from camera 256. Patient capture module 254 may perform image processing (e.g., face detection, segmentation, shape detection to detect human form, etc.) on the video stream to detect when a patient is present, and may capture one or more reference digital images of the patient (e.g., the intake digital images described below) in response to the detection. In some embodiments, the reference digital images may be captured at a higher resolution than individual frames of the video stream, although this is not required. In some embodiments, camera 256 may be a standalone camera, such as a webcam, a PTZ camera (e.g., 276), and so forth, that is deployed in or near pre-waiting room area(s) 102. Subsets of the intake digital images captured by camera 256 may be used to generate subject reference templates and corresponding template feature vectors that are associated with registered patients (and more generally, “subjects”) and used later to identify and/or locate registered patients in the area being monitored.

Patient queue module 258 may be configured to establish and/or maintain a priority queue, e.g., in a database, of the order in which patients in the area should be monitored. In various embodiments, the queue may be ordered by various parameters. In some embodiments, patients in the queue may be ranked in order of patient acuity measures (i.e. by priority). For example, the most critical patients may be placed at the front of the queue more frequently than less critical patients. In some embodiments, updated vital signs may be acquired from patients waiting in the area being monitored, such as waiting room 104, in an order of the queue. In other embodiments, updated vital signs may be acquired from patients in a FIFO or round robin order. In other embodiments, updated vital signs may be acquired from patients in an order that corresponds to a predetermined scan trajectory programmed into vital sign acquisition camera 276 (e.g., scan each row of chairs in order).

Patient identification module 260 may be configured with selected aspects of the present disclosure to use one or more digital images captured by vital sign acquisition camera 276 (or another camera that is not configured to acquire vital signs unobtrusively), in conjunction with subject reference templates and/or corresponding template feature vectors captured by patient capture module 254, to locate one or more patients in the area being monitored (e.g., waiting room 104). Patient identification module 260 may analyze acquired digital images using various techniques described below to identify and locate patients (subjects). FIGS. 4-10, described below, demonstrate various aspects of various techniques that may be employed as part of recognizing/identifying/locating patients, or more generally, subjects, in any context.

In some embodiments, patient identification module 260 may search an area being monitored for particular patients from which to obtain updated vital signs. For example, patient identification module 260 may search the area being monitored for a patient selected by patient queue module 258, which may be, for instance, the patient in the queue having the highest patient acuity measure. In some embodiments, patient identification module 260 may cause vital sign acquisition camera(s) 276 to scan the area being monitored (e.g., waiting room 104) until the selected patient is identified.

Dynamic calibration module 262 may be configured to track the use of vital sign acquisition camera(s) 276 and calibrate them as needed. For instance, dynamic calibration module 262 may ensure that whenever vital sign acquisition camera 276 is instructed to point to a particular PTZ location, it always points to the exact same place. PTZ cameras may be in constant or at least frequent motion. Accordingly, their mechanical components may be subject to wear and tear. Small mechanical errors/biases may accumulate and cause vital sign acquisition camera 276 to respond, over time, differently to a given PTZ command Dynamic calibration module 262 may correct this, for instance, by occasionally running a calibration routine in which landmarks (e.g., indicia such as small stickers on the wall) may be used to train a correction mechanism that will make vital sign acquisition camera 276 respond appropriately

Once a patient identified by patient queue module 258 is recognized/located by patient identification module 260, face/torso acquisition module 264 may be configured to pan, tilt, and/or zoom one or more vital sign acquisition cameras 276 so that their fields of view capture a desired portion of the patient. For example, in some embodiments, face/torso acquisition module 264 may pan, tilt, or zoom a vital sign acquisition camera 276 so that it is focused on a patient's face and/or upper torso. Additionally or alternatively, face/torso acquisition module 264 may pan, tilt, or zoom one vital sign acquisition camera 276 to capture predominantly the patient's face, and another to predominantly capture the patient's torso. Various vital signs and/or physiological parameters may then be acquired. For instance, vital signs such as the patient's pulse rate and SpO₂ may be obtained, e.g., by vital signs measurement module 266, by performing image processing on an video of the patient's face captured by vital sign acquisition camera(s) 276. Vital signs and/or physiological parameters such as the patient's respiratory rate, and so forth may be obtained, e.g., by vital signs measurement module 266, by performing image processing on an video of the patient's torso captured by vital sign acquisition camera(s) 276. Of course, the face and torso are just two examples of body portions that may be examined to obtain vital signs, and are not meant to be limiting.

Deterioration detection module 268 may be configured to analyze various signals and/or data to determine whether a condition of a registered patient (or even non-registered companions) is deteriorating, improving, and/or remaining stable. In some embodiments, the patient condition may be represented, at least in part, by the same patient acuity measures described above for determining order of patients for monitoring. As such, the deterioration detection module 268 may include one or more CDS, case-based reasoning, or other clinical reasoning algorithms as described herein or other clinical reasoning algorithms (e.g., trained logistic regression models or other machine learning models) for assessing patient condition measures other than acuity measures described herein. In some embodiments, the algorithms for assessing patient acuity or other measures of patient condition employed by the deterioration detection module 268 may be updated from time to time by, for example, writing new trained weights (e.g., theta values) for a selected machine learning model or providing new instructions for execution by a processor (e.g. in the form of a java archive, JAR, file or compiled library). These signals may include, for instance, a patient's initial vital signs and other physiological information (e.g., obtained at blocks 108-110 of FIG. 1), updated vital signs obtained by vital signs measurement module 266, a patients initial patient acuity measure (e.g., calculated during registration), and/or a patient's updated patient acuity measure (e.g., calculated based on updated vital signs and/or physiological parameters received from vital signs measurement module 266).

Based on determinations made using these data and/or signals, deterioration detection module 268 may send various alerts to various other modules to take various actions. For example, deterioration detection module 268 may publish an alert, e.g., by sending the alert to EPS module 270 so that EPS module can publish the alert to subscribed modules, such as alarm module 248 of hospital information system 240. In some embodiments, such an alert may include, for instance, a patient's name (or more generally, a patient identifier), a picture, live video stream, the patient's last detected location in the waiting room, baseline vital signs, one or more updated vital signs, and/or an indication of a patient acuity measure. On receipt of the alert, alarm module 248 may raise an alert or alarm to medical personnel of the patient's deterioration and, among other things, the patient's last detected location in the waiting room.

EPS module 270 may be a general communication hub that is configured to distribute events released by various other components of FIG. 2. In some embodiments, all or at least some of the other modules depicted in FIG. 2 may generate events that indicate some form of result/determination/computation/decision from that module. These events may be sent, or “published,” to EPS module 270. All or some of the other modules depicted in FIG. 2 may elect to receive, or “subscribe to,” any event from any other module. When EPS module 270 receives an event, it may send data indicative of the event (e.g., forward the event) to all modules that have subscribed to that event.

In some embodiments, EPS module 270 may be in communication with one or more databases, such as database 272 and/or archive 274 (which may be optional). In some embodiments, EPS module 270 may accept remote procedure calls (“RPC”) from any module to provide access to information stored in one or more databases 272 and/or 274, and/or to add information (e.g., alerts) received from other modules to databases 272 and/or 274. Database 272 (which may be the same as subject reference database 412 in some embodiments) may store information contained in alerts, publications, or other communications sent/broadcast/transmitted by one or more other modules in FIG. 2. In some embodiments, database 272 may store, for instance, subject reference templates associated with patients and/or their initial vital signs, updated vital signs (acquired by vital sign acquisition camera 276), and/or patient acuity measures. Optional archive 274 may in some embodiments store the same or similar information for a longer period of time.

It will be apparent that various hardware arrangements may be utilized to implement the patient monitoring system 252. For example, in some embodiments, a single device may implement the entire system 252 (e.g., a single server to operate the camera 276 to perform the vital signs acquisition functions 260-266 and to perform the vital sign(s) analysis and alerting functions including deterioration detection 268 and patient queue management 258). In other embodiments, multiple independent devices may form the system 252. For example, a first device may drive the vital sign acquisition camera 276 and implement functions 260-266 while another device(s) may perform the remaining functions. In some such embodiments, one device may be local to the waiting room while another may be remote (e.g., implemented as a virtual machine in a geographically distant cloud computing architecture). In some embodiments, a device (e.g., including a processor and memory) may be disposed within the vital sign acquisition camera 276 itself and, as such, the camera 276 may not simply be a dumb peripheral and, instead may perform the vital signs functions 260-266. In some such embodiments, another server may provide indications (e.g. identifiers, full records, or registered facial images) to the camera 276 to request that vitals be returned for further processing. In some such embodiments, additional functionality may be provided on-board the camera 276 such as, for example, the deterioration detection 268 (or preprocessing therefor) and/or patient queue module 258 management may be performed on-board the camera 276. In some embodiments, the camera 276 may even implement the HIS interface 250 or EPS 270. Various additional arrangements will be apparent.

FIG. 3 illustrates an example scenario in which disclosed techniques may be implemented to identify patients 378A-C in a waiting room 304 for monitoring purposes. In this example, three patients 378A-C are waiting in a hospital waiting room 304 to be attended to by medical personnel 380. Two video cameras 376A, 376B are mounted on a surface (e.g., ceiling, wall) of waiting room 304. The two video cameras 376A, 376B may be used to monitor patients 378 in waiting room 304. The patients 378A-C may each be assigned a patient acuity measure by triaging medical personnel (not depicted) based on a preliminary patient condition analysis. As the patients 378 wait for an attending physician, the two video cameras 376A, 376B may capture digital image(s) that are analyzed using techniques described herein to identify patients selected for monitoring. The same video cameras (assuming they are configured to unobtrusively acquire vital signs) or different video cameras may then be operated to monitor patients 378 as described above, e.g., to detect patient deterioration. In some embodiments, a patient acuity measure associated with a patient may be updated by medical personnel in response to detection by patient monitoring system (more specifically, deterioration detection module 268) that a patient has deteriorated. In various embodiments, when a new patient enters waiting room 304, a new round of patient monitoring and prioritization may be performed, e.g., by patient monitoring system 252. The patient queue may be automatically updated, e.g., by patient queue module 258, each time a new patient enters waiting room 304. Additionally or alternatively, medical personnel may manually update the patient queue to include a newly-arrived patient after triaging.

Techniques described herein are not limited to hospital waiting rooms. There are numerous other scenarios in which techniques described herein may be implemented to identify/locate subjects in digital images or videos. For example, disclosed techniques may also be used for security monitoring of crowds in airports, arenas, border crossings, and other public places. In such scenarios, rather than monitoring patients to determine patient acuity measures, subjects may be identified for other purposes, such as risk assessments or post-event investigation. Techniques described herein may also be applicable in scenarios such as in fitness environments (e.g., gyms, nursing homes) or other surveillance scenarios (e.g., airports, border crossings, etc.) in which identification of individual subjects depicted in digital images may be implemented. For example, in airports, subjects waiting at gates could be identified, for example, by comparing images of subjects waiting at gates to subject reference templates obtained at check-in and/or from passport/identification photos. In addition, techniques described herein may be used to identify patients who left without being seen, without requiring that patients' faces be visible.

FIG. 4 schematically depicts, at a relatively high level, an example of components configured with selected aspects of the present disclosure, as well as example interactions between those components. In various embodiments, one or more of these components may be implemented using any combination of hardware and software, e.g., as part of patient monitoring system 252 in FIG. 2 and particularly as part of patient capture module 254 and patient identification module 260. For example, the components of FIG. 4 may be used at block 108 of FIG. 1 to register a subject such as a patient in a subject reference database 412. Along with the subjects' intake information (e.g., age, gender, name, initial vital signs, etc.), any number of “subject reference templates” that comprise digital images of the subject's face from multiple views (e.g., different angles, different facial expressions, different lighting conditions, different head positions, etc.) may be selected and associated with the subject in the subject reference database 412, e.g., by way of a medical record number (“MRN”). These subject reference templates (and as described below, template feature vectors generated from these subject reference templates) may then be used later, e.g., by patient identification module 260, to identify the subject in an area such as a waiting room using another camera (e.g., vital sign acquisition cameras 276, 376) that captures the waiting room in its field of view. Once the subject is identified, the subject's location can be used for various purposes, such as being contacted by medical personnel, having vital signs unobtrusively acquired, etc.

Starting at bottom right, an intake routine 402 is depicted that includes operations for intake of a newly-registered subject (e.g., registering and/or triaging a new patient) and adding that subject to a subject reference database 412, in accordance with various embodiments. A first camera 456 may be configured to capture one or more of what will be referred to herein as “intake” digital images 404 (e.g., individual images and/or a stream of images such as a video stream). First camera 456, which may correspond to camera 256 in FIG. 2 in some instances, may take various forms, such as a webcam positioned in the intake area (e.g., registration and/or triage), a camera integral with a computing device operated by intake personnel (e.g., a triage nurse), etc. This image capture may be un-intrusive to both the intake personnel and the subject, as it may occur automatically with little or no human intervention (although this is not meant to be limiting).

At block 406, intake digital image(s) 404 may be analyzed, e.g., by one or more computing systems operably coupled with camera 456 (e.g., patient capture module 254 in FIG. 2) to detect one or more portions of digital images 404 that depict a face of a subject currently located in an intake area (e.g., registration and/or triage). FIG. 6 demonstrates one example technique for detecting the subject's face. Other techniques may include, for example, genetic algorithms, eigen-face techniques, template matching, etc. In some embodiments, one or more of the intake digital image(s) 404 may be cropped or otherwise altered (e.g., background cropped) to focus on the subject's face, although this is not required.

At block 408, a subset of intake digital images that depict multiple different views of a face of the subject may be selected from plurality of intake digital images 404. The selected subset may be used to generate subject reference templates that are used to visually identify/locate the subject later. In some embodiments, the subset of intake digital images used to generate the subject reference templates may be selected based on being sufficiently dissimilar to one or more other intake digital images. FIGS. 5 and 8 below demonstrate example techniques for selecting subsets of intake images for generation of subject reference templates.

In some embodiments, at block 409, the subject reference templates generated at block 408 may be applied as input across a machine learning model, such as a convolutional neural network, to generate what will be referred to herein as “template feature vectors.” These template feature vectors may include a variety of features in addition to or instead of the raw data of the subject reference templates. Convolutional neural networks in particular have recently shown improvements over other face recognition approaches. A convolutional neural network may be trained with millions (or more) of face images that include a variety of head poses, facial expressions, lighting conditions, etc., to ensure that the convolutional neural network is usable to generate template feature vectors (and other feature vectors described below) that are more discriminative than the source image alone. In some embodiments, the convolutional neural network may comprise a stack of convolution, regularization, and pooling layers. In some embodiments, one or more graphical processing units (“GPUs”) may be employed to perform feature extraction using the convolutional neural networks, as they may be able to do so more efficiently than standard central processing units (“CPUs”).

Examples of suitable convolutional neural networks that may be employed to generate various feature vectors (a.k.a. “vectorized descriptors,” “embedded descriptors,” “embeddings,” etc.) described herein, as well as how they may be trained, are described in O. M. Parkhi, A. Vedaldi, A. Zisserman, Deep Face Recognition, British Machine Vision Conference (2015); Yaniv Taigman, Ming Yang, Marc'Aurelio Ranzato, Lior Wolf, DeepFace: Closing the Gap to Human-Level Performance in Face Verification, IEEE International Conference on Computer Vision and Pattern Recognition (2014): and Florian Schroff, Dmitry Kalenichenko, James Philbin, FaceNet: A Unified Embedding for Face Recognition and Clustering, IEEE International Conference on Computer Vision and Pattern Recognition (2015). Generally speaking, these publications describe training a convolutional neural network to learn a mapping from face images to a compact Euclidian space in which distances between embeddings directly correspond to a measure of face similarity. Once this compact Euclidian space has been determined, face recognition can be implemented using the embeddings as feature vectors, such as the aforementioned template feature vectors. In various embodiments, the convolutional neural networks may be trained by minimizing a softmax loss at the last network layer with each subject identity as a unique class label. The loss may then be back-propagated to all previous layers to gradually update all the coefficients in each layer. The back-propagation may be iteratively executed, e.g., thousands of times. During each iteration, as few as dozens or hundreds of face images may be randomly sampled from the collected millions of training face images to be used for the loss minimization.

At block 410, the generated subject reference templates and corresponding template feature vectors may be stored, e.g., in subject reference database 412, in association with the subject. In various embodiments, the generated subject reference templates and template feature vectors may be stored in subject reference database 412 in association with information related to the subject, e.g., by way of the aforementioned MRN. More generally, subject reference database 412 may store subject reference templates and associated template feature vectors related to a plurality of subjects, such as a plurality of registered patients in waiting room 104 that may be awaiting medical treatment. In other embodiments, template feature vectors associated with registered subjects may be generated on an as-needed and/or on-demand basis.

A subject identification routine 418 is depicted at top left that may be performed, for instance, by patient identification module 260 of FIG. 2 using another camera 476, which may or may not take the form of a vital sign acquisition camera described previously. Subject identification routine 418 may be performed at various times in response to various events, periodically, continuously, etc. In some embodiments, a subject may be sought out as part of a subject monitoring routine 414 in which personnel such as a nurse issues a query seeking to locate a particular subject. In other embodiments, subject identification routine 418 may be performed continuously as part of the ongoing effort described previously to monitor patients' acuity. In some embodiments, camera 476 may be cycled through each detected subject to determine the detected subject's identity and associate it with the detected subject's location.

Subject identification routine 418 may begin with the acquisition of digital images 420 (e.g., a video stream) that depict an area in which a queried subject or subjects generally are believed to be, such as waiting room 104. At block 422, one or more portions of the digital image(s) 420 that depict a face of a particular subject in the area may be detected, e.g., by patient identification module 260, as what will be referred to herein as “detected face images.” In various embodiments, the operations of block 422 may be performed continuously and/or may be triggered by receipt of the subject query from patient monitoring routine 414. Similar techniques for face detection may be applied at block 422 as were applied at block 406, some of which will be described in more detail below.

In some embodiments, at block 423, one or more adjustments may be made, e.g., to calibrate images 420 acquired by camera 476 as closely as possible with intake digital images 404 acquired by camera 456 (or, e.g., 256). Various operations may be performed at block 423 to achieve this calibration. In some embodiments, one or more settings of camera 476 such as aperture, exposure, shutter speed, white balance, etc. may be made to align the settings with corresponding settings of camera 456. Aperture (size of the opening through which light travels to light sensor) and shutter speed (amount of time light sensor is exposed to light) in particular are optical adjustments. Decreasing aperture size increases image sharpness and makes the resulting image darker. Shorter shutter time reduces motion blur and also tends to make the resulting image darker. A camera's aperture and shutter speed settings typically are discrete, i.e., they are adjustable in steps of approximately √2 times in diameter, which corresponds to factor of two change in light intensity. Likewise, the shutter speed can typically also be controlled in steps of two times. This discreteness may in some cases limit the accuracy of image adjustments. In contrast to these optical adjustments, an electronic adjustment that can be made to one or more cameras is a white balance adjustment in individual gains associated with red, green, and/or blue (RGB).

Additionally or alternatively, in some embodiments, adjustments may be made (e.g., using image processing software process(es)) to digital images (404, 420) acquired by one or both cameras (e.g., 456 and/or 476) to calibrate the images to each other. For example, in some embodiments, intake digital images 404 and/or later-acquired digital images 420 may be color corrected, e.g., using one or more image processing software processes, to adjust brightness, adjust hue, etc. Additionally or alternatively, in some embodiments, various image processing techniques may be performed to achieve head pose correction between intake digital images 404 and later-acquired digital images 420.

In some embodiments, at block 424, a subset (or “keyframes”) of the one or more detected face images generated at block 422 may be selected that represent the greatest variation of depictions of the detected subject's face, e.g., depicting different poses, positions, lighting, facial expressions, etc. In some embodiments, a process similar to that depicted in FIG. 8 may be used to select the subset of detected face images (or “keyframes”). At block 425, one or more operations may be performed to normalize (or “frontalize”) the faces depicted in the detected face images. For example, in some embodiments, geometric warping and/or other similar techniques may be employed to normalize detected faces to be at or near frontal views. FIG. 7 described below demonstrates one example technique for normalizing detected faces. Thus, the output of block 425 may be one or more normalized detected face images of a particular subject in the area being monitored.

At block 426, a process referred to herein as “feature comparison” may be employed to determine the particular subject's identity by matching the particular subject to a registered subject in subject reference database 412. The process of “feature comparison is described in more detail below with regard to FIG. 9. At block 428, the identity of the detected subject and/or the detected subject's location (e.g., a particular location such as a seat in a waiting room at which the subject is located) may be provided as output. At block 430, camera 476 may be panned, tilted, and/or zoomed, e.g., to capture a subject (if any) at a next location of a sequence of locations (e.g., chairs in waiting room 104).

FIG. 5 depicts one example of how various aspects of the workflow of intake routine 402 of FIG. 4 may be implemented, in accordance with various embodiments. As described above, camera 456 may acquire intake digital images 404, e.g., as a video stream. In some embodiments, intake digital images 404 may depict an intake (e.g., triage) area, although this is not required. The operations depicted in FIG. 5 may be performed at various computing devices, such as a computing device that is operably coupled with camera 456 in or near the intake area.

In the intake (e.g., triage) area where a new subject is assessed (e.g., clinically assessed), for each new intake digital image (e.g., frame of a video stream) captured by camera 456, at blocks 502 and 504, respectively, face detection (e.g., of a new face) and face tracking (e.g., of a face detected in a previous intake digital image) may be performed in parallel. This ensures that a face of each subject in the intake area is detected, no matter which subject entered first. For each newly detected face, at block 506, a new face tracker is launched. This new face tracker will start its analysis at the next image frame. Then, at block 508, the newly detected face is normalized, e.g., to a near-frontal view (normalization is demonstrated in more detail in FIG. 7).

In some embodiments, this normalized detected face may be deemed a subject template candidate. Then, the new subject reference template candidate may be compared, e.g., at block 510, with existing subject reference template candidates (e.g., acquired from previous image frames), if any yet exist. Various criteria may be used to determine whether to keep the new subject reference template candidate, e.g., as a replacement of another previously-captured subject reference template candidate, or to discard the new subject reference template candidate. Ultimately, only the most representative subject reference templates candidates may be selected and retained in subject reference database 412. FIG. 8 demonstrates, in greater detail, one example of how intake digital images may be selected (510) for use in generating subject reference templates.

Turning now to face tracking block 504, for each tracked face previously detected in each intake image frame, at block 512, it may be determined whether the corresponding subject is leaving the camera's field of view. FIG. 6 depicts one example of how a determination may be made of whether a subject is leaving. If the answer at block 512 is yes, then operation passes back to block 504 and the next tracked face is selected. If the answer at block 512 is no, then at block 514, homography estimation may be performed, e.g., to estimate a three-dimensional head pose of the tracked face in the current intake image frame. Based on the estimated pose, the tracked face image in the current frame may be “frontalized” (removing the pose effect on face appearance) at block 516. Control may then pass to block 508.

FIG. 6 demonstrates one example technique for detecting a subject's face, e.g., during intake (e.g., at block 406) or later during subject monitoring (e.g., at block 422). A camera's field of view (“FOV”) 640 is shown, and may be associated with any camera described herein, such as camera 456 or camera 476. FIG. 6 illustrates the both detection of a subject (642A) entering and a subject (642B) leaving. Both situations only happen when the subject's face is partially visible in FOV 640. The presence of a subject may be detected, for instance, by measuring the overlapping ratio of a face region to FOV 640. If the ratio is less than a particular number, such as one, and is increasing compared to the previous frame(s), the subject may be determined to be entering. Otherwise, if the ratio is greater than one and is decreasing compared to the previous frame(s), the subject may be determined to be leaving. If either of the two situations lasts for a predetermined time interval, such as five seconds, it is possible to determine that the subject has entered or left.

FIG. 7 depicts details of one example face normalization routine, e.g., that may be performed at block 425 of FIG. 4 and/or block 508 of FIG. 5. Input may take the form of a detected face image, e.g., from block 422 or block 424 of FIG. 4 and/or from block 506/516 of FIG. 5. Output may be a normalized detected face image. At blocks 702 and 704, left and right eye detection operations may be performed (operations 702 and 704 may also be performed in the reverse order, or in parallel). These operations may include a variety of image processing techniques, such as edge detection, template matching, Eigenspace methods, Hough transforms, morphological operations, trained neural networks, etc. At block 706, if both eyes are successfully detected, control may pass to block 714, at which point the face may be normalized (e.g., geometric warping may be applied to the detected face image to make the face approximately frontal facing). From block 714, control may pass, for instance, to block 426 of FIG. 4 or to block 510 of FIG. 5.

If the answer at block 706 is no, then at block 708 it may be determined whether either eye was detected. If the answer is no, then control may pass downstream of operation 714, in some instances a failure event may be raised, and then control may proceed, e.g., to block 426 of FIG. 4 or to block 510 of FIG. 5. If only one eye was successfully detected at blocks 702-704, then at block 710, the detected eye region may be mirrored horizontally, and the mirror eye patch may be searched, e.g., using template matching, to locate the other eye. Then, operation may proceed to block 714, which was described previously.

FIG. 8 depicts one example of how detected face images may be selected as subject reference templates, e.g., for inclusion in subject reference database 412, at block 408 of FIG. 4 and block 510 of FIG. 5. Control may pass to the operations of FIG. 8 from various locations, such as block 406 of FIG. 4, block 508 of FIG. 5 (if the detected face image under consideration is newly detected in the current intake digital image frame), and/or block 516 of FIG. 5 (if the detected face image under consideration was detected in a prior intake digital image frame and is currently being tracked). At block 802, it may be determined whether the face is occluded. If the answer is yes, then control may pass to block 504, at which point the next tracked face (if any) may be analyzed.

If the answer at block 802 is no, then at block 806, image similarities between the current detected face image and any existing subject reference templates for the current subject may be determined. At block 808, it may be determined whether there are yet enough subject reference templates collected for the current subject. Various numbers of subject reference templates may be selected for each new subject. In some embodiments, as many as nine subject reference templates may be collected. While collecting more subject reference templates is feasible, diminishing returns may be experienced after some point.

If there are not yet enough subject reference templates collected for the current subject, then at blocks 408-410 (same as FIG. 4), the current detected face image may be used to generate a subject reference template (408), a corresponding template feature vector may be generated (409), and both may then be added (410) to subject reference database 412. However, at block 808, if there are already enough templates collected, then in some embodiments, it may be determined whether the current detected face image is sufficiently different from previously-collected subject reference templates of the current subject to warrant replacing a previously-collected subject reference template. For example, at block, at block 812, a determination may be made of whether the current detected face image is more dissimilar from each previously-collected subject reference template than any of the previously-collected subject reference templates are from each other. If the answer is yes for a particular subject reference template, then the current detected face image may be used to generate a new subject reference template (409) that replaces the particular subject reference template in subject reference database 412. For example, a corresponding template feature vector may be generated 409, and the template and feature vector may be added (410) to subject reference database 412.

The operations of FIG. 8 (and more generally, the operations of FIG. 5) may be repeated for every intake digital image captured by camera 456, and each subject may be tracked, for instance, until they leave the intake area (block 512). Consequently, of the total number of intake digital images acquired while the subject is in FOV 640 of camera 456, the n intake digital images having the most suitably (e.g., most diverse) views may be selected to generate subject reference templates for that particular subject. As mentioned previously, these subject reference templates and/or corresponding template feature vectors may be used later, e.g., in response to a subject being queried at subject monitoring routine 414.

FIGS. 5 and 8 relate to collecting subject reference templates and corresponding template feature vectors for each subject to be stored in subject reference database 412. FIGS. 6 and 7 relate to both to collecting subject reference templates and using those subject reference templates to identify subjects in areas downstream from intake areas, such as hospital waiting rooms. FIG. 9 relates to the latter. In particular, FIG. 9 depicts one example of operations that may be performed, e.g., by patient identification module 260, as part of the “feature comparison” block 426 of FIG. 4, as well as blocks 427 and 428 of FIG. 4.

In FIG. 9, two inputs are received: the current detected face image(s) under consideration and subject reference templates from subject reference database 412. As shown in FIG. 9, the current detected face image(s) may be generated based on digital images (e.g., 420 in FIG. 4) acquired from a camera 976 (or 476 in FIG. 4) that is deployed in an area such as waiting room 104. While not depicted in FIG. 9, in various embodiments, one or more of the operations of blocks 422-425 in FIG. 4 may be performed to generate the detected face images received as input in FIG. 9.

At block 902, the detected face image(s) may be applied as input across a machine learning model, such as the convolutional neural network described above, to generate (at block 904) so-called “face feature vectors” (also referred to as “vectorized descriptors”) associated with one or more of the detected face images. In some embodiments, the same convolutional neural network(s) may be used as was used at block 409 of FIG. 4 to generate the template feature vectors that are stored in subject reference database 412 with the subject reference templates. Meanwhile, at block 906, all registered subjects' template feature vectors may be retrieved and/or located in subject reference database 412. In other embodiments, all registered subjects' template feature vectors may be generated on the fly, e.g., contemporaneously with operations of block 902 using the same convolutional neural network.

In some embodiments, at block 908, distances between one or more face feature vectors 904 (e.g., an average of multiple face feature vectors) and template feature vectors 906 may be determined. The distances between the feature vectors may or may not be Euclidian distances, and may be determined in various ways, such as using cosine similarity, dot products, etc. In some embodiments, the distances (or other measures of similarity) may be used as part of a nearest neighbor (“NN”) search in which one or more template feature vectors that are most similar to (e.g., shortest Euclidian distance from) the face feature vector(s) under consideration may be identified. In some embodiments, the first and second nearest neighbors may be identified, and may be associated with NN and NN_2^(nd) scores that may be, for instance, so-called “correlation scores” that are inversely related to respective Euclidian distances from the face feature vector(s), and thus represent similarity measures.

In some embodiments, a relationship, ratio, etc. between the NN score and the NN_2^(nd) score may be analyzed to determine whether the nearest neighbor template feature vector (which recall corresponds to a registered subject in subject reference database 412) is sufficiently more similar to the face feature vector (which corresponds to the detected subject) than the second nearest neighbor template feature vector (corresponding to another registered subject in subject reference database 412). For example, at block 910, a determination may be made of whether NN score/NN_2^(nd) score is greater than some predetermined threshold (e.g., which may be manually set, learned empirically, etc.). If the answer is yes, that suggests that, intuitively, the nearest neighbor template feature vector is a substantially better match for the detected subject than the second nearest neighbor, and thus the nearest neighbor likely corresponds to the same subject as the detected face image(s). On the other hand, if the answer is no, then the nearest neighbor is not substantially a better match than the second nearest neighbor.

Assuming the answer at block 910 is yes, then in some embodiments, a determination may be made of whether the current detected face image(s) and/or face feature vector under consideration should be stored as what will be referred to herein as an “auxiliary subject reference template” and an “auxiliary template feature vector,” respectively. Auxiliary subject reference templates and/or their corresponding auxiliary template feature vectors may be used to supplement or supplant existing subject reference templates/template feature vectors already stored in subject reference database 412. That is, auxiliary subject reference templates and/or auxiliary template feature vectors may be used subsequently to more accurately identify subjects in areas such as waiting room 104. In some embodiments, only the auxiliary template feature vector may be stored in subject reference database 412, though this is not required.

Storing such auxiliary data may give rise to a variety of technical advantages. Auxiliary subject reference templates/auxiliary template feature vectors are usually generated using digital images (e.g., 420) acquired by a different camera (e.g., 276, 376, 476, 976) than subject reference templates generated during registration (e.g., which may be captured using a camera such as camera 256, 456). Subject reference templates and their corresponding template feature vectors generated at registration are based on intake digital images 404 in which the subject is in a controlled setting (e.g., triage, registration, etc.) and is likely facing the camera. By contrast, auxiliary subject reference templates and their corresponding auxiliary template feature vectors are generated based on digital images (e.g., 420) acquired in a less controlled setting such as waiting room 104. Consequently, auxiliary subject reference templates/template feature vectors may be generated from digital images that depict the subject from various angles (and in most cases not looking at or near camera), in lighting that is different than the lighting at registration/triage, and so forth.

Perhaps more importantly, auxiliary subject reference templates/template feature vectors may more accurately represent the subject in his or her current state, e.g., sitting in waiting room 104 reading a magazine. Accordingly, if a face feature vector can be confidently matched to the subject, then that face feature vector may be a good candidate to generate and store an auxiliary template feature vector for future use. As more auxiliary template feature vectors are generated for a subject over time, these auxiliary template feature vectors may enable more accurate identification of the subject in a variety of (e.g., post-waiting room 104) settings than the original template feature vectors generated at registration.

Referring back to FIG. 9, in some embodiments, at block 912, a determination may be made of whether the NN score (e.g., correlation score) determined at block 908 for the nearest neighbor template feature vector is greater than a correlation score calculated (e.g., based on a Euclidian distance) between the face feature vector under consideration and any auxiliary template feature vectors that already exist for the registered subject that corresponds to nearest neighbor. If the answer is yes (or if there are not yet any auxiliary template feature vectors for the nearest neighbor), then at block 916, the face feature vector may be added as a new auxiliary template feature vector to subject reference database 412 for future use. In some embodiments, the detected face image itself may also be added as an auxiliary subject reference template, though this is not required.

Then, at block 914 (or 428 of FIG. 4), the identity (and/or location such as a waiting room chair) of the detected subject may be provided, e.g., as output to medical personnel, or to aid in unobtrusive acquisition of vital signs from the subject using one or more vital sign acquisition cameras. If the answer at block 912 is no—meaning there are already one or more “better” auxiliary template feature vectors stored in subject reference database 412 for the subject—then control may pass directly to block 914 without adding a new auxiliary template feature vector to subject reference database 412.

In some cases, the subject reference templates and/or corresponding template feature vectors generated during registration may not be sufficient to identify a subject depicted in detected face images. For example, suppose digital image(s) (e.g., 420) acquired of a subject in a waiting room are vastly different from intake digital images 404 acquired during registration (e.g., due to different angles, lighting, etc.). In such a circumstance it is possible that a detected subject may be a relatively close match to more than one registered subject. For example, at block 910 of FIG. 9, it may be determined that the nearest neighbor is not sufficiently more similar to the face feature vector than the second nearest neighbor (e.g., that NN/NN_2^(nd)<the aforementioned threshold).

In such a scenario, auxiliary template feature vectors may prove particularly useful. For example, if the answer at block 910 is no, then at block 918, it may be determined whether there exist (e.g., in subject reference database 412) any auxiliary template feature vectors associated with the registered subject corresponding to the nearest neighbor. If the answer is yes, then at block 920, a new NN score may be calculated, e.g., as a Euclidian distance between the auxiliary template feature vector of the nearest neighbor and the face feature vector currently under consideration. Similar operations may be performed at blocks 922 and 924 for the second nearest neighbor to generate a new NN_2^(nd) score. Then, at block 926, the new NN score and the new NN_2^(nd) score may be analyzed, e.g., to determine whether a ratio between them (e.g., determined using equations such as NN/NN_2^(nd) or NN_2^(nd)/NN) satisfies a predetermined threshold (e.g., the same threshold as at block 910 or a different threshold). If the answer is yes, then control may pass to block 914 (described above); otherwise at block 928 no decision as to the identity of the detected subject is made (e.g., output of “inconclusive” is provided).

FIG. 10 depicts an example method 1000 for practicing selected aspects of the present disclosure, in accordance with various embodiments. For convenience, the operations of the flow chart are described with reference to a system that performs the operations. This system may include various components of various computer systems, including patient monitoring system 252. Moreover, while operations of method 1000 are shown in a particular order, this is not meant to be limiting. One or more operations may be reordered, omitted or added.

At block 1002, the system may acquire, e.g., from a first camera (e.g., 276, 376, 476), one or more digital images (e.g., video frames) that depict a subject in an area such as waiting room 104. For example, in some embodiments, the system may acquire a video feed that includes a plurality of digital images acquired by the first digital camera. At block 1004, the system may detect, as one or more detected face images, one or more portions of the one or more digital images that depict a face of the subject. In various embodiments, techniques similar to those that were employed at block 406 of FIG. 4 (of which one example is described in more detail in FIG. 6) may be used to detect faces. In some embodiments, head poses that are as much as forty to forty five degrees from facing the camera may be usable to detect faces. As noted above, in some embodiments, “keyframes” of multiple digital images (e.g., a video stream) may be selected (e.g., at block 424) that depict a variety of different poses, facial expressions, etc. of the detected subject. And in various embodiments, the digital images (e.g., the keyframes) may be analyzed using various facial detection techniques (e.g., template comparisons) and may be cropped, have their backgrounds removed, etc., so that the detected face images only or primarily include the subject's face.

At block 1006, the system may compare features of the one or more detected face images with features of subject reference templates associated with one or more subjects in subject reference database (412). Additionally or alternatively, the system may compare features of the one or more detected face images with auxiliary template feature vectors associated with the subject(s). Notably, the subject reference templates were generated based on intake digital images (404) acquired by a second camera (e.g., 256, 456), whereas the auxiliary template feature vectors were generated based on digital image(s) acquired by a different, second camera (e.g., 276, 376, 476). Accordingly, and as noted above, the auxiliary template feature vectors may more closely represent the subject's current state (e.g., sitting in waiting room 104, not looking at the camera), and therefore may enhance the ability, e.g., of patient identification module 260, to accurately identify the subject.

In various embodiments, the comparing of block 1006 may include operations such as the system applying (at block 1008) the detected face images as input across one or more neural networks (e.g., convolutional neural networks described above) to generate corresponding face feature vectors. At block 1010, the system may compare the generated face feature vectors to template feature vectors that were generated from application (which may have occurred, for instance, during or immediately following registration/triage) of the subject reference templates across the same or different neural networks. As noted previously, because the subject reference templates were generated based on intake digital images 404 acquired by a second camera (e.g., 256, 456), the template feature vectors were also generated based on digital images acquired by the second camera. At block 1012, the system may additionally or alternatively compare the face feature vectors to auxiliary template feature vectors that were generated based on digital images (e.g., 420) acquired by the first camera (e.g., 276, 376, 476), not the second camera. As noted above, one or more of the comparing operations of blocks 1008-1012 may involve determining Euclidian distances using various techniques, such as dot product, cosine similarity, joint embedding, etc.

At block 1014, based on the comparing, an identity of the subject may be determined. Also based on the comparing—e.g., if features of the detected face images are sufficiently closer to a nearest neighbor than a second nearest neighbor—at block 1016, features of the one or more detected face images may be stored in subject reference database 412 in association with the subject, e.g., as an auxiliary template feature vector. For example, in some embodiments, the system may determine a first (e.g., Euclidian) distance between a face feature vector generated from one or more of the detected face images and a first template feature vector generated from a subject reference template(s) associated with a first subject in subject reference database 412. The system may likewise determine a second distance between the face feature vector and a second template feature vector generated from subject reference template(s) associated with a second subject in subject reference database 412. In some cases, these distances (and additional distances if there are additional registered subjects) may be used as part of the nearest neighbor search described above with respect to block 908 to calculate the aforementioned “correlation scores” that are directly related to similarity. Based on a relationship between the first and second correlation scores, which may correspond to the NN score and the NN_2^(nd) score described previously, the face feature vector may be stored as an auxiliary template feature vector in subject reference database 412.

The subject's identity determined at block 1016 may be used for various purposes. In some embodiments, the location of the subject depicted in the original digital images (acquired at block 1002) may be determined, e.g., based on PTZ settings of the camera that captured the digital images. For example, in some embodiments, the camera may be configured to scan through a plurality of locations, such as chairs in waiting room 104, looking for subjects at each location. When a subject is detected at a particular location and then matched to a registered subject, the subject's identity may be provided, e.g., as audio or visual output to a duty nurse or other medical personnel, along with a location of the subject. In some embodiments, the identity/location may be output to other modules of patient monitoring system 252.

In other scenarios, a location of a particular registered subject (e.g., a queried subject) may be desired, e.g., so that the subject's vital signs can be monitored (e.g., unobtrusively using camera 276), the subject can be taken to see a doctor, etc. In such a situation, method 1000 may be performed for each subject that is detected by one or more cameras monitoring an area such as waiting room 104 until the sought-after subject is located. In some such scenarios, if the queried subject is not found—e.g., because the subject was admitted into a treatment area of an emergency department or the subject left without being seen—pertinent personnel (e.g., hospital staff) may be notified. If the subject left temporarily, e.g., to use the restroom, the subject may be reinserted into the patient queue described above so that they can be monitored at a later time.

FIG. 11 is a block diagram of an example computer system 1110. Computer system 1110 typically includes at least one processor 1114 which communicates with a number of peripheral devices via bus subsystem 1112. As used herein, the term “processor” will be understood to encompass various devices capable of performing the various functionalities attributed to components described herein such as, for example, microprocessors, GPUs, FPGAs, ASICs, other similar devices, and combinations thereof. These peripheral devices may include a data retention subsystem 1124, including, for example, a memory subsystem 1125 and a file storage subsystem 1126, user interface output devices 1120, user interface input devices 1122, and a network interface subsystem 1116. The input and output devices allow user interaction with computer system 1110. Network interface subsystem 1116 provides an interface to outside networks and is coupled to corresponding interface devices in other computer systems.

User interface input devices 1122 may include a keyboard, pointing devices such as a mouse, trackball, touchpad, or graphics tablet, a scanner, a touchscreen incorporated into the display, audio input devices such as voice recognition systems, microphones, and/or other types of input devices. In general, use of the term “input device” is intended to include all possible types of devices and ways to input information into computer system 1110 or onto a communication network.

User interface output devices 1120 may include a display subsystem, a printer, a fax machine, or non-visual displays such as audio output devices. The display subsystem may include a cathode ray tube (CRT), a flat-panel device such as a liquid crystal display (LCD), a projection device, or some other mechanism for creating a visible image. The display subsystem may also provide non-visual display such as via audio output devices. In general, use of the term “output device” is intended to include all possible types of devices and ways to output information from computer system 1110 to the user or to another machine or computer system.

Data retention system 1124 stores programming and data constructs that provide the functionality of some or all of the modules described herein. For example, the data retention system 1124 may include the logic to perform selected aspects of FIGS. 4-10, and/or to implement one or more components of patient monitoring system 252, including patient identification module 260, patient capture module 254, etc.

These software modules are generally executed by processor 1114 alone or in combination with other processors. Memory 1125 used in the storage subsystem can include a number of memories including a main random access memory (RAM) 1130 for storage of instructions and data during program execution, a read only memory (ROM) 1132 in which fixed instructions are stored, and other types of memories such as instruction/data caches (which may additionally or alternatively be integral with at least one processor 1114). A file storage subsystem 1126 can provide persistent storage for program and data files, and may include a hard disk drive, a floppy disk drive along with associated removable media, a CD-ROM drive, an optical drive, or removable media cartridges. The modules implementing the functionality of certain implementations may be stored by file storage subsystem 1126 in the data retention system 1124, or in other machines accessible by the processor(s) 1114. As used herein, the term “non-transitory computer-readable medium” will be understood to encompass both volatile memory (e.g. DRAM and SRAM) and non-volatile memory (e.g. flash memory, magnetic storage, and optical storage) but to exclude transitory signals.

Bus subsystem 1112 provides a mechanism for letting the various components and subsystems of computer system 1110 communicate with each other as intended. Although bus subsystem 1112 is shown schematically as a single bus, alternative implementations of the bus subsystem may use multiple busses. In some embodiments, particularly where computer system 1110 comprises multiple individual computing devices connected via one or more networks, one or more busses could be added and/or replaced with wired or wireless networking connections.

Computer system 1110 can be of varying types including a workstation, server, computing cluster, blade server, server farm, or any other data processing system or computing device. In some embodiments, computer system 1110 may be implemented within a cloud computing environment. Due to the ever-changing nature of computers and networks, the description of computer system 1110 depicted in FIG. 11 is intended only as a specific example for purposes of illustrating some implementations. Many other configurations of computer system 1110 are possible having more or fewer components than the computer system depicted in FIG. 11.

While several embodiments have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein, and each of such variations and/or modifications is deemed to be within the scope of the embodiments described herein. More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific embodiments described herein. It is, therefore, to be understood that the foregoing embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, embodiments may be practiced otherwise than as specifically described and claimed. Inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the scope of the present disclosure.

All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and/or ordinary meanings of the defined terms.

The indefinite articles “a” and “an,” as used herein in the specification and in the claims, unless clearly indicated to the contrary, should be understood to mean “at least one.”

The phrase “and/or,” as used herein in the specification and in the claims, should be understood to mean “either or both” of the elements so conjoined, i.e., elements that are conjunctively present in some cases and disjunctively present in other cases. Multiple elements listed with “and/or” should be construed in the same fashion, i.e., “one or more” of the elements so conjoined. Other elements may optionally be present other than the elements specifically identified by the “and/or” clause, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, a reference to “A and/or B”, when used in conjunction with open-ended language such as “comprising” can refer, in one embodiment, to A only (optionally including elements other than B); in another embodiment, to B only (optionally including elements other than A); in yet another embodiment, to both A and B (optionally including other elements); etc.

As used herein in the specification and in the claims, “or” should be understood to have the same meaning as “and/or” as defined above. For example, when separating items in a list, “or” or “and/or” shall be interpreted as being inclusive, i.e., the inclusion of at least one, but also including more than one, of a number or list of elements, and, optionally, additional unlisted items. Only terms clearly indicated to the contrary, such as “only one of” or “exactly one of,” or, when used in the claims, “consisting of,” will refer to the inclusion of exactly one element of a number or list of elements. In general, the term “or” as used herein shall only be interpreted as indicating exclusive alternatives (i.e. “one or the other but not both”) when preceded by terms of exclusivity, such as “either,” “one of,” “only one of,” or “exactly one of.” “Consisting essentially of,” when used in the claims, shall have its ordinary meaning as used in the field of patent law.

As used herein in the specification and in the claims, the phrase “at least one,” in reference to a list of one or more elements, should be understood to mean at least one element selected from any one or more of the elements in the list of elements, but not necessarily including at least one of each and every element specifically listed within the list of elements and not excluding any combinations of elements in the list of elements. This definition also allows that elements may optionally be present other than the elements specifically identified within the list of elements to which the phrase “at least one” refers, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, “at least one of A and B” (or, equivalently, “at least one of A or B,” or, equivalently “at least one of A and/or B”) can refer, in one embodiment, to at least one, optionally including more than one, A, with no B present (and optionally including elements other than B); in another embodiment, to at least one, optionally including more than one, B, with no A present (and optionally including elements other than A); in yet another embodiment, to at least one, optionally including more than one, A, and at least one, optionally including more than one, B (and optionally including other elements); etc.

It should also be understood that, unless clearly indicated to the contrary, in any methods claimed herein that include more than one step or act, the order of the steps or acts of the method is not necessarily limited to the order in which the steps or acts of the method are recited.

In the claims, as well as in the specification above, all transitional phrases such as “comprising,” “including,” “carrying,” “having,” “containing,” “involving,” “holding,” “composed of,” and the like are to be understood to be open-ended, i.e., to mean including but not limited to. Only the transitional phrases “consisting of” and “consisting essentially of” shall be closed or semi-closed transitional phrases, respectively, as set forth in the United States Patent Office Manual of Patent Examining Procedures, Section 2111.03. It should be understood that certain expressions and reference signs used in the claims pursuant to Rule 6.2(b) of the Patent Cooperation Treaty (“PCT”) do not limit the scope. 

What is claimed is:
 1. A method implemented by one or more processors, the method comprising: acquiring, using a first camera, one or more digital images that depict a subject in an area; detecting, as one or more detected face images associated with the subject, one or more portions of the one or more digital images that depict a face of the subject; comparing features of the one or more detected face images with features of subject reference templates associated with one or more subjects in a subject reference database, wherein the comparing comprises: determining a first distance between a face feature vector generated from one or more of the detected face images and a first template feature vector generated from a first subject reference template associated with a first subject in the subject reference database; and determining a second distance between the face feature vector and a second template feature vector generated from a subject reference template associated with a second subject in the subject reference database; wherein the subject reference database stores subject reference templates related to a plurality of subjects, and wherein the subject reference templates stored in the subject reference database are generated and stored based on data contemporaneously received from a second camera; wherein, for each given subject reference template, the given subject reference template is associated with an identity of one of the plurality of subjects contemporaneously with the given subject reference template being generated; and based on the comparing: determining an identity of the subject, and storing the features of the one or more detected face images in the subject reference database in association with the subject as an auxiliary template feature vector for later use, wherein the storing is based on a relationship between the first and second distances.
 2. The method of claim 1, wherein the comparing comprises: applying the one or more detected face images as input across a neural network to generate one or more corresponding face feature vectors; and applying at least some of the subject reference templates as input across the neural network to generate a plurality of corresponding template feature vectors.
 3. The method of claim 2, wherein the neural network comprises a convolutional neural network.
 4. The method of claim 1, wherein the second camera is located in a registration or triage area.
 5. The method of claim 4, wherein the first camera is located in a waiting room or general ward.
 6. The method of claim 1, further comprising: acquiring, using the first camera, one or more subsequent digital images that depict a second subject in the area; detecting, as one or more detected face images associated with the second subject, one or more portions of the one or more subsequent digital images that depict a face of the second subject; and comparing features of the one or more detected face images associated with the second subject with features of auxiliary subject reference templates associated with one or more subjects in the subject reference database, wherein the auxiliary subject reference templates are generated based on digital images captured by the first camera to determine an identity of the second subject.
 7. The method of claim 1, wherein the auxiliary template feature vector replaces an existing template feature vector associated with the subject.
 8. A system comprising one or more processors and memory operably coupled with the one or more processors, wherein the memory stores instructions that, in response to execution of the instructions by one or more processors, cause the one or more processors to: acquire, using a first camera, one or more digital images that depict a subject in an area; detect, as one or more detected face images associated with the subject, one or more portions of the one or more digital images that depict a face of the subject; compare features of the one or more detected face images with features of subject reference templates associated with one or more subjects in a subject reference database, wherein the instructions to compare include instructions to: determine a first distance between a face feature vector generated from one or more of the detected face images and a first template feature vector generated from a first subject reference template associated with a first subject in the subject reference database; and determine a second distance between the face feature vector and a second template feature vector generated from a subject reference template associated with a second subject in the subject reference database, wherein the subject reference database stores subject reference templates associated with a plurality of subjects, and wherein the subject reference templates stored in the subject reference database are generated and stored based on data contemporaneously received from a second camera; wherein, for each given subject reference template, the given subject reference template is associated with an identity of one of the plurality of subjects contemporaneously with the given subject reference template being generated; and based on the comparison: determine an identity of the subject, and store the features of the one or more detected face images in the subject reference database in association with the subject as an auxiliary template feature vector, wherein the storage is based on a relationship between the first and second distances.
 9. The system of claim 8, wherein the comparison comprises: applying the one or more detected face images as input across a neural network to generate one or more corresponding face feature vectors; and applying at least some of the subject reference templates as input across the neural network to generate a plurality of corresponding template feature vectors.
 10. The system of claim 9, wherein the neural network comprises a convolutional neural network.
 11. The system of claim 8, wherein the second camera is located in a registration or triage area.
 12. The system of claim 11, wherein the first camera is located in a waiting room or general ward.
 13. The system of claim 8, further comprising instructions to: acquire, using the first camera, one or more subsequent digital images that depict a second subject in the area; detect, as one or more detected face images associated with the second subject, one or more portions of the one or more subsequent digital images that depict a face of the second subject; and compare features of the one or more detected face images associated with the second subject with features of auxiliary subject reference templates associated with one or more subjects in the subject reference database, wherein the auxiliary subject reference templates are generated based on digital images captured by the first camera to determine an identity of the second subject.
 14. The system of claim 8, wherein the auxiliary template feature vector replaces an existing template feature vector associated with the subject.
 15. At least one non-transitory computer-readable medium comprising instructions that, in response to execution of the instructions by one or more processors, cause the one or more processors to perform the following operations: acquiring, using a first camera, one or more digital images that depict a subject in an area; detecting, as one or more detected face images associated with the subject, one or more portions of the one or more digital images that depict a face of the subject; comparing features of the one or more detected face images with features of subject reference templates associated with one or more subjects in a subject reference database, wherein the subject reference database stores subject reference templates associated with a plurality of subjects, wherein the subject reference templates stored in the subject reference database are generated and stored based on data contemporaneously received from a second camera, and wherein, for each given subject reference template, the given subject reference template is associated with an identity of one of the plurality of subjects contemporaneously with the given subject reference template being generated, wherein the comparing comprises: determining a first distance between a face feature vector generated from one or more of the detected face images and a first template feature vector generated from a first subject reference template associated with a first subject in the subject reference database; and determining a second distance between the face feature vector and a second template feature vector generated from a subject reference template associated with a second subject in the subject reference database; and based on the comparing: determining an identity of the subject, and storing the features of the one or more detected face images in the subject reference database in association with the subject as an auxiliary template feature vector, wherein the storing is based on a relationship between the first and second distances. 